To help you manage access to on a Web server, FrontPage provides you with a simple role-based model and useful administrative tools for setting permissions. The role-based model simply says that the permissions you give a user depend on that user's role (a user can be a person, group, or computer).
For each on a Web server, you can set permissions for users in the following three roles:
FrontPage-extended web permissions are hierarchical: A user with administrative permissions has authoring and browsing permissions. A user with authoring permissions has browsing permissions.
By default, the permissions you set for a web are inherited by all the subwebs below it. You can, however, set unique permissions for a subweb that override the permissions it inherited from its parent web. That way, you can specify different levels of access to each subweb for each user or group. For example, you can give the same user authoring permissions for one subweb but only browsing permissions for another.
For which users can you set permissions? The answer depends on the Web server you are working with. Microsoft Internet Information Services (IIS) supplies user accounts from the Windows NT account list. You can set permissions only for users on this list; you cannot create new user accounts. For other Web servers, however, the list of users is maintained by the Web server and you can create new user accounts.
You can set permissions for a web in FrontPage by using the FrontPage Server Extensions utilities, such as Fpsrvadm, as well as the Permissions command on the Tools menu.